-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull Request automation in krel release-notes #1304
Pull Request automation in krel release-notes #1304
Conversation
47c2f5e
to
9a84972
Compare
For reference, kubernetes-sigs/release-notes#153 was automatically generated using these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I just have a couple of nits.
I had forgotten to cc the team |
9a84972
to
d875d4c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold
Feel free to lift the hold if you want to address the branch issue in a follow-up PR.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: puerco, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I'm merging this one and I'll start fixing the issue found in kubernetes-sigs/release-notes#153 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR automates the creation of pull requests to update the release notes draft in
k/sig-release
and the release notes website inksigs/release-notes
. It mainly puts to work changes to the github library merged in #1287 and #1268 so most of the work was already in place.It also verifies that the repositories used by the user are actual forks of their kubernetes counterparts..
Which issue(s) this PR fixes:
Related to #834
Special notes for your reviewer:
I've broken the PR into two commits, one for the automation of the release notes draft and one for the website patches.
The website portion is a bit temporary and will be removed soon as we are about to begin implementing some changes to move the json files to a GCP bucket. I plan to refactor some of the release notes subcommand code before that.
Does this PR introduce a user-facing change?
After this patch, running krel with
--create-draft-pr
or--create-website-pr
will now really create pull requests in github.